Skip to content

docs: admin guide for kernel keyring sysctl settings (Docker-in-LXC quota fix)#280

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/fix-session-keyring-error
Draft

docs: admin guide for kernel keyring sysctl settings (Docker-in-LXC quota fix)#280
Copilot wants to merge 2 commits intomainfrom
copilot/fix-session-keyring-error

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 7, 2026

runc inside unprivileged LXC containers exhausts the per-UID kernel keyring quota, crashing Docker builds with unable to create session key: disk quota exceeded. The fix is host-level — raise the kernel limits so the container's unprivileged UID gets the same ceiling as real host root.

Changes

  • docs/admins/kernel-keyring.md — new page covering:
    • The two required sysctls and their rationale (unprivileged container root vs. host root limits under nested virtualization)
    • Immediate (sysctl -w) and persistent (/etc/sysctl.d/) application methods
  • docs/admins/index.md — linked the new page
# /etc/sysctl.d/99-kernel-keys.conf
kernel.keys.maxkeys=200000
kernel.keys.maxbytes=2000000

Apply on every Proxmox node running Docker-in-LXC workloads, then sysctl --system.

Copilot AI changed the title [WIP] Fix bug unable to join session keyring due to disk quota docs: admin guide for kernel keyring sysctl settings (Docker-in-LXC quota fix) Apr 7, 2026
Copilot AI requested a review from runleveldev April 7, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: unable to join session keyring: unable to create session key: disk quota exceeded

2 participants